System and method for performing time-flexible calendric storage operations

ABSTRACT

A system and method are provided for creating a non-standard calendar that may have customized attributes, such as number of days in a month, first day of a month, number of months in a year, first month of a year, number of years, or other customized attributes. Such non-standard calendars may be similar to non-standard calendars used by companies, enterprises or other organizations, such as a fiscal calendar, academic calendar, or other calendar. A storage management system manager may have a database of storage policies that include preferences and frequencies for performing storage operations, and associations with a non-standard calendar. The storage manager can initiate storage operations based on the storage policy using data that may be identified according to selection criteria, and determine a time to perform the storage operation according to a non-standard calendar.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. application Ser. No.12/467,863, filed May 18, 2009, entitled SYSTEM AND METHOD FORPERFORMING TIME-FLEXIBLE CALENDRIC STORAGE OPERATIONS, which claimspriority to U.S. application Ser. No. 11/313,225, filed Dec. 19, 2005,entitled SYSTEM AND METHOD FOR PERFORMING TIME-FLEXIBLE CALENDRICSTORAGE OPERATIONS, the entirety of each of which are herebyincorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosures, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND OF THE INVENTION Field of the Invention

The invention disclosed herein relates generally to performing timeflexible storage operations.

Current storage management systems employ a number of different methodsto perform storage operations on electronic data. Such storageoperations may be scheduled in a job queue, which may be scheduled basedon a calendar. In conventional storage systems, the calendar used toschedule storage operations is a standard Gregorian calendar which, inone calendar year beginning January and ending in December, has twelvemonths, each having a predefined number of days in each month totaling365 days per year, and 366 days in a leap year. Some enterprises,companies, users or other entities have specialized non-standardcalendars for enterprise operations. Such calendars may be differentthan the standard Gregorian calendar. For example, a company may chooseto follow a fiscal calendar and begin its calendar in April, an academicinstitution may choose to begin its year after Labor Day, a toy companymay choose to begin its year on the first Friday after Thanksgiving,another company may wish to begin its week on a Wednesday, and otherentities may have other such calendars. When a company has a specializedcalendar, it is convenient to schedule all aspects of the company orentity according to the calendar.

SUMMARY OF THE INVENTION

Systems and methods are described herein for performing time flexiblestorage operations. In one embodiment, a method for performing a storageoperation is provided including: receiving a non-standard calendar and astorage policy, the storage policy including data indicating a frequencyfor performing a storage operation; determining, based on the frequency,a time corresponding to frequency according to the non-standardcalendar; and at the time, initiating the storage operation. Data forperforming the storage operation may be identified according to aselection criterion. If it is determined that the time occurs after afirst term of the non-standard calendar expired; a second term of thenon-standard calendar may be predicted, wherein the time occurs duringthe second term; and wherein the first term and the second term of thenon-standard calendar include at least one common time flexiblepreference.

In another embodiment, a method for scheduling a storage operation, isprovided including receiving data indicating a non-standard calendar;associating the non-standard calendar with a storage policy; based onthe storage policy, determining a frequency for performing a storageoperation; determining a storage operation time, the storage operationtime corresponding to the frequency for performing the storage operationusing the non-standard calendar; and scheduling the storage operation tobe performed in a Gregorian calendar based storage management system atthe storage operation time. An indication of an association of thenon-standard calendar and the storage policy may be stored in an index.If the storage operation time comprises a time before or after a firstterm of the non-standard calendar, an alert may be transmitted, and/or asecond term of the non-standard calendar may be predicted, wherein thestorage operation time occurs during the second term; and wherein thefirst term and the second term of the non-standard calendar include atleast one common time flexible preference. Data for performing thestorage operation may be identified according to a selection criterion.

In another embodiment, a method for scheduling a storage operation isprovided including receiving a storage policy, the storage policyincluding a frequency for performing a storage operation; based on aselection criteria, identifying a data item for performing the storageoperation, identifying a non-standard calendar associated with thestorage policy; determining a time to perform the storage operation, thetime corresponding to the frequency for performing the storage operationbased on the non-standard calendar; and at the determined time,performing the storage operation. The selection criteria may be a timecriterion to which a corresponding time may be determined based on thenon-standard calendar. The non-standard calendar may be identified forthe storage operation as the non-standard calendar associated with thestorage policy in an index. Examples of storage operations may be aselective deletion operation, a selective copy operation, or a retentionoperation. If the determined time for performing the storage operationoccurs after a first term of the non-standard calendar expired; a secondterm of the non-standard calendar may be predicted, wherein thedetermined time occurs during the second term; and wherein the firstterm and the second term of the non-standard calendar include at leastone common time flexible preference.

In another embodiment, a storage management system for scheduling astorage operation, is provided including a calendar modulecommunicatively coupled to a year module, a month module, a day module,and a offset module; the calendar module communicatively coupled to astorage manager and an index; wherein the year module, month module, daymodule and offset module are programmed to provide a non-standardcalendar; wherein the index is capable of storing data indicating anassociation of the non-standard calendar and a storage policy; andwherein the storage manager is programmed to consult the storage policyin the index, determine a time to perform a storage operation accordingto the storage policy and non-standard calendar, and direct the storageoperation at the determined time.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is illustrated in the figures of the accompanying drawingswhich are meant to be exemplary and not limiting, in which likereferences are intended to refer to like or corresponding parts, and inwhich:

FIG. 1 is a block diagram of a storage system according to an embodimentof the invention;

FIG. 2 is a block diagram of an aspect of the storage system of FIG. 1according to an embodiment of the invention;

FIG. 3 is a table of calendar data according to an embodiment of theinvention;

FIG. 4 is a graphical user interface for defining a calendar accordingto an embodiment of the invention;

FIG. 5 is a graphical user interface for defining months in a calendaraccording to an embodiment of the invention;

FIGS. 6 and 7 are flow diagrams for performing a storage operationaccording to embodiments of the invention;

FIG. 8 is a graphical user interface for associating a non-standardcalendar with a storage operation according to an embodiment of theinvention;

FIGS. 9 and 10 are graphical user interfaces for scheduling a storageoperation according to embodiments of the invention;

FIG. 11 is a flow diagram for performing a storage operation accordingto an embodiment of the invention; and

FIGS. 12-14 are graphical user interfaces for entering rules forperforming storage operations according to an embodiment of theinvention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

With reference to FIGS. 1 through 14, embodiments and features of theinvention are presented. FIG. 1 illustrates a block diagram of a storageoperation cell 50 that may perform storage operations on electronic datain a computer network in accordance with an embodiment of the presentinvention. As shown, storage operation cell 50 may generally include astorage manager 100, a data agent 95, a media agent 105, a storagedevice 115, and, in some embodiments, may include certain othercomponents such as a client 85, a data or information store 90,databases or indexes 110 and 111, jobs agent 120, an interface module125, and a management agent 130. Such system and elements thereof areexemplary of a modular storage management system such as the CommVaultQiNetix system, and the CommVault GALAXY backup system, available fromCommVault Systems, Inc. of Oceanport, N.J.

A storage operation cell, such as cell 50, may generally includecombinations of hardware and software components associated withperforming storage operations on electronic data. Storage operationcells generally are capable of performing storage operations and othertypes of storage management functions. In accordance with the invention,additional storage operations performed by storage operation cells mayinclude creating, storing, retrieving, and migrating primary data copiesand secondary data copies (which may include, for example, snapshotcopies, backup copies, HSM copies, archive copies, and other types ofcopies of electronic data). In some embodiments, storage operation cellsmay also provide one or more integrated management consoles for users orsystem processes to interface with in order to perform certain storageoperations on electronic data as further described herein. Suchintegrated management consoles may be displayed at a central controlfacility or several similar consoles distributed throughout multiplenetwork locations to provide global or geographically specific networkdata storage information.

In some embodiments, storage operations may be performed according to astorage policy. A storage policy is generally a data structure or otherinformation source that includes a set of preferences and other storagecriteria for performing a storage operation. The preferences and storagecriteria may include, but are not limited to, a storage location,relationships between system components, relationships between systemcomponents and use of a third party application, network pathway toutilize, retention policies, data characteristics, compression orencryption requirements, preferred system components to utilize in astorage operation, and other criteria relating to a storage operation.Thus, a storage policy may indicate that certain data is to be stored ina specific storage device, retained for a specified period of time,which may be based on a flexible non-standard calendar, before beingaged to another tier of secondary storage, retained, copied, or deletedaccording to specific criteria, copied to secondary storage using areplication copy or a specified number of streams, a frequency forperforming storage operations, etc. A storage policy may be stored to astorage manager database or index 111, to archive media as metadata foruse in restore operations or other storage operations, or to otherlocations or components of the system. The storage policy may beassociated with a standard calendar or a non-standard calendar, forexample, by storing an indication or pointer in the index 111 of therelationship between the storage policy and the calendar.

As described herein, a non-standard calendar may be useful in storagemanagement applications because the calendar used by the storagemanagement system can conform to a particular calendar in use in anenterprise, company or other entity. A storage management systemnon-standard calendar facilitates and enables scheduling storageoperations following a non-standard or other existing calendar in usefor other enterprise operations, such as inventory management, salesperformance tracking, revenue reporting, financial modeling, or otheraspect of an enterprise. Alternatively, a non-standard calendar can beused to define a storage operation schedule according to an enterprise'srequirements, which may not necessarily follow a particular orstandard/Gregorian calendar.

A schedule policy may specify a frequency, or when and how often toperform a storage operation, the calendar on which to base a storageoperation schedule, and may also specify performing certain storageoperations on sub-clients of data and how to treat those sub-clients.Schedule policy information may be included in a storage policy, orassociated with a storage policy.

A sub-client may represent static or dynamic associations of portions ofdata of a volume and are mutually exclusive. Thus, a portion of data maybe given a label and the association is stored as a static entity in anindex, database or other storage location used by the system.Sub-clients may also be used as an effective administrative scheme oforganizing data according to data type, department within theenterprise, storage preferences, etc. For example, a sub-client may beall media in an associated storage device and the sub-client isassociated with a non-standard calendar and storage policy whichrequires that certain storage operations be performed on a schedule orat a particular frequency that is based on the non-standard calendar.

A storage preference may be a storage policy, user preference or otherstorage preference associated with performance of storage operations. Insome embodiments the storage preference is defined by a system user orsystem administrator. In other embodiments, the storage preference is adefault preference. Examples of storage preferences can include: anon-standard calendar to use for storage operations, data securitysettings, encryption settings, data retention requirements, frequency ofstorage operations, such as frequency of backups, types of data forstorage operations, such as data types for backups, types of storageoperations to perform in the component group, network pathways, such aspreferred network pathways to perform a storage operation, scheduling,such as a schedule of storage operations, reports, such as automaticgeneration of system reports regarding the group, which can include, forexample, the storage operations performed by the group, or other storagepreference.

A storage operation cell may be associated with a storage policy,schedule policy, storage preferences, user preferences, non-standardcalendar or other storage rules or preferences. The storage operationcell may be automatically configured for storage needs and associatedwith a particular user, application, data type, organization, departmentor other group. For example, in a financial company, one or more storageoperation cells may be configured to handle data generated by a New Yorkoffice, a particular application, one or more clients, one or moretrader's data, financial data, financial trades data, email, documents,or other class of data. Each storage operation cell may be associatedwith a storage policy which sets forth the storage requirements for thecell. In addition, a non-standard calendar may be associated with thecell or storage policy which may dictate a special or customizedcalendar for performing storage operations.

Storage operation cells may contain not only physical devices, but alsomay represent logical concepts, organizations, and hierarchies. Forexample, a first storage operation cell 50 may be configured to performa storage operation, such as data backup or other types of datamigration, and may include a variety of physical components including astorage manager 100 (or management agent 130), a media agent 105, aclient component 85, and other components as described herein. A secondstorage operation cell may contain the same or similar physicalcomponents, however, it may be configured to perform other storageoperations, such as monitoring a primary data copy or replication copyvolume or performing other known storage operations.

Data agent 95 may be a software module or part of a software module thatis generally responsible for archiving, migrating, and recovering datafrom client computer 85 stored in an information store 90, or othermemory location. Each client computer 85 may have at least one dataagent 95 and the system can support multiple client computers 85. Insome embodiments, data agents 95 may be distributed between client 85and storage manager 100 (and any other intermediate components (notshown)) or may be deployed from a remote location or its functionsapproximated by a remote process that performs some or all of thefunctions of data agent 95.

Embodiments of the present invention may employ multiple data agents 95each of which may backup, migrate, and recover data associated with adifferent application. For example, different individual data agents 95may be designed to handle MICROSOFT EXCHANGE data, LOTUS NOTES data,MICROSOFT WINDOWS 2000 file system data, MICROSOFT ACTIVE DIRECTORYOBJECTS data, and other types of data known in the art. Otherembodiments may employ one or more generic data agents 95 that canhandle and process multiple data types rather than using the specializeddata agents described above.

Generally speaking, storage manager 100 may be a software module orother application that coordinates and controls storage operationsperformed by storage operation cell 50. Storage manager 100 maycommunicate with some or all elements of storage operation cell 50including client computers 85, data agents 95, media agents 105, andstorage devices 115, to initiate and manage system backups, migrations,and data recovery.

Referring to FIG. 2, the storage manager 100 may have access to anon-standard calendar 240, which may be created and customized using acalendar module 220. The calendar module 220 may be a separate module,or its functionality may be provided by the storage manager 100 or othercell component. The calendar module 220 may customize a calendaraccording to preferences, which may be time-related, time-flexible, andwhich may be provided via a user input or a user preference, or viastorage policy, storage template, or other input. For example,information or a data file relating to a standard or Gregorian calendar210 may be input into the calendar customization module and calendarpreferences entered via one or more of the month module 222, day module224, year module 225, and offset module 226. The functionality of eachof the calendar module 200, month module 222, day module 224, yearmodule 225, and offset module 226 is further described herein. Aresulting non-standard calendar 240 may be stored in a database, datatable or index.

Referring again to FIG. 1, storage manager 100 may also include a jobsagent 120 that monitors the status of some or all storage operationspreviously performed, currently being performed, or scheduled to beperformed by storage operation cell 50. For example, the jobs agent 120may consult a storage policy and a non-standard calendar to monitor andschedule storage operations. Jobs agent 120 may be communicativelycoupled with an interface agent 125 (typically a software module orapplication). Interface agent 125 may include information processing anddisplay software, such as a graphical user interface (“GUI”), anapplication program interface (“API”), or other interactive interfacethrough which users and system processes can retrieve information aboutthe status of storage operations.

Through interface 125, users may optionally issue instructions tovarious storage operation cells 50 regarding performance of the storageoperations as described and contemplated herein. For example, a user maymodify a schedule concerning a calendar or other schedule for pendingcopies or other types of copies as needed to suit particular needs orrequirements. As another example, a user may employ the GUI to view thestatus of pending storage operations in some or all of the storageoperation cells in a given network or to monitor the status of certaincomponents in a particular storage operation cell (e.g., the amount ofstorage capacity left in a particular storage device). As a furtherexample, interface 125 may display the calendar associated with aparticular cell or type of data storage and may allow a user todetermine overall scheduling associated with a particular data type, orcertain storage operation cell 50 or other storage operation aspredefined or user-defined.

Storage manager 100 may also include a management agent 130 that istypically implemented as a software module or application program. Ingeneral, management agent 130 provides an interface that allows variousmanagement components 100 in other storage operation cells 50 tocommunicate with one another. For example, assume a certain networkconfiguration includes multiple cells 50 adjacent to one another orotherwise logically related in a WAN or LAN configuration (not shown).With this arrangement, each cell 50 may be connected to another cellthrough each respective interface module 125. This allows each cell 50to send and receive certain pertinent information from other cells 50including status information, routing information, information regardingcapacity and utilization, etc. These communication paths may also beused to convey information and instructions regarding storageoperations.

Storage manager 100 may also maintain an index cache, a database, orother data structure 111. The data stored in database 111 may be used toindicate logical associations between components of the system, userpreferences, management tasks, storage policies, associations ofnon-standard calendars, some SRM or HSM data or other useful data. Asfurther described herein, some of this information may be stored in amedia agent database 110 or other local data store according to someembodiments. For example, the storage manager 100 may use data fromdatabase 111 to track logical associations of primary copies of data,storage policies, non-standard calendars, media agents 105 and storagedevices 115 or between other components of the system.

Generally speaking, a media agent 105 may be implemented as a softwaremodule that conveys data, as directed by a storage manager 100, betweena client computer 85 and one or more storage devices 115 such as a tapelibrary, a magnetic media storage device, an optical media storagedevice, or any other suitable storage device. In one embodiment, mediaagents 105 may be communicatively coupled with and control a storagedevice 115 associated with that particular media agent. A media agent105 may be considered to be associated with a particular storage device115 if that media agent 105 is capable of routing and storing data to aparticular storage device 115.

In operation, a media agent 105 associated with a particular storagedevice 115 may instruct the storage device to use a robotic arm or otherretrieval means to load or eject a certain storage media, and tosubsequently archive, migrate, or restore data to or from that media.Media agents 105 may communicate with a storage device 115 via asuitable communications path such as a SCSI or fiber channelcommunications link. In some embodiments, the storage device 115 may becommunicatively coupled to a data agent 105 via a Storage Area Network(“SAN”).

Each media agent 105 may maintain an index cache, a database, or otherdata structure 110 which stores index data generated during backup,migration, and restore and other storage operations as described herein.For example, performing storage operations on MICROSOFT EXCHANGE datamay generate index data. Such index data provides a media agent 105 orother external device with a fast and efficient mechanism for locatingdata stored or backed up. Thus, in some embodiments, a storage managerdatabase 111 may store data associating a client 85 with a particularcalendar, a particular media agent 105 or storage device 115, forexample, as specified in a storage policy, while media agent database110 may indicate where specifically the client 85 data is stored instorage device 115, what specific files were stored, and otherinformation associated with storage of client 85 data. In someembodiments, such index data may be stored along with the data backed upin a storage device 115, with an additional copy of the index datawritten to index cache 110. The data in index cache 110 is thus readilyavailable for use in storage operations and other activities withouthaving to be first retrieved from the storage device 115.

In some embodiments, certain components may reside and execute on thesame computer. For example, in some embodiments, a client computer 85such as a data agent 95, a media agent 105, or a storage manager 100coordinates and directs local archiving, migration, and retrievalapplication functions as further described in U.S. patent applicationSer. No. 09/610,738. This client computer 85 can function independentlyor together with other similar client computers 85.

Referring again to FIG. 2, a storage manager 100 may initiate a storageoperation based on a storage policy, which may be stored in a database111, and a non-standard calendar 240. For example, a storage policy maydictate that a storage operation may be performed on a weekly, monthly,yearly basis, or other frequency. Non-standard calendar 240 is generallya calendar which may be based on a Gregorian or standard calendar 210that has been customized or defined using a calendar module 220. Thecalendar module 220 may include one or more modules, such as monthmodule 222, day module 224, year module 225, offset module 226 whichprovide functionality for customizing aspects of the non-standardcalendar 240. The functionality of the modules 222, 224, 225, 226 may beprovided by one or more modules. A month module 222 may be used tospecify and associate month-specific preferences. For example, a monthmodule 222 may set the number of months in a year, the first month ofthe year or other month related preference, for a non-standard calendar.Day module 224 may be used to set day-related calendar preferences, suchas the number of days in a month, or other day specification. Yearmodule 226 may be used to define year-related preferences, such as thenumber of years in a non-standard calendar, a first year in thecalendar, or other year preference. The offset module 226 may be used tospecify an offset for beginning a month on a particular day or beginninga year on a particular month, such as the 5.sup.th of the month, secondMonday of a month, third month of the year, or other offset.

The non-standard calendar 240 may comprise a data file that may includeone or more data items such as the data shown in the table of FIG. 3. Asshown, calendar table 300 may include information and fields associatedwith a non-standard calendar such as an ID 320 or name for the calendar,first year 325, number of years 330, first month 335, first date 340,months per year 345, days per month 350, default 355, operations 360,storage policy 365 or other information. The non-standard calendar ID320 can be any name, and may be user selected or automaticallygenerated, e.g., based on a storage cell or storage operation. Thenon-standard calendar ID may be used to differentiate calendars whenmore than one calendar is used in a storage management system. The firstyear 325 is the initial or starting year of the calendar.

The number of years 330 may set the duration or term of the calendar. Atthe end of the non-standard calendar term, a user or systemadministrator may be notified that the non-standard calendar term hasended. Any storage operation requests received after the non-standardcalendar term may fail or may require remedying. One example ofremedying a storage operation request which is associated with anexpired non-standard calendar may be provided by a storage manager,calendar module or other system component which may analyze the expirednon-standard calendar associated with the storage operation request, andgenerate a predicted further term which has many or all of the calendarpreferences or customizations included in the expired non-standardcalendar. For example, if a two-year long non-standard calendar iscreated in which each year begins April 16.sup.th and each month has aset number of days, at the end of the two year term, a storage manager,calendar module or other system component may extend the non-standardcalendar for another year beginning April 16.sup.th and having months ofthe same number of days. In the event that a calendar has expired andthe system attempts to remedy a storage operation request and associatednon-standard calendar, an alert may be sent which indicates that suchaction was taken and which may suggest that an expired calendar beextended or created anew.

Data relating to year preferences may be handled by a year module orother module. The first month 340 is the starting month of the calendar.For example, as shown, a fiscal calendar may begin in April, an academiccalendar may begin in September, or other month may be used to commencethe calendar year. Month preferences may be handled by a month module orother module. The first day of a month 340 may indicate the beginningdate of a month or the first month. Day preferences may be handled by anoffset module, day module, or other module. For example, for anon-standard calendar with settings that the 3rd is a first day of thefirst month of the calendar, there are 28 days in a month according tothe day per month setting 350, the calendar automatically calculates thebeginning of the next month, which would be 28 days after the 3rd day ofthe first month of the calendar. Calendars may be assigned an arbitrarynumber of months per year 345, for example, each year could have 6months, 3 months or other number of months. Each calendar may be set asa default 355 calendar to use, in connection with cell components,storage policies, storage preferences, system component, storageoperations, a particular user, application or data types, or otherstorage characteristic. Non-standard calendars may also be associatedwith particular storage operations 360, such as for use in selectivedeletion operations, selective copy operations, retention operations,migrations, restores, or other storage operations. In addition,non-standard calendars can also be associated with a storage policy 365.As described herein, storage policy information can include scheduling,a frequency, and other preferences for performing storage operations.Thus, in association with a non-standard calendar, a storage manager mayinitiate a storage operation according to a storage policy preferenceand using a non-standard calendar, e.g., a default non-standard calendaras defined in or associated with a storage policy.

The information stored in the table 300 may be received as user oradministrator input. Alternatively, templates for non-standard calendarsmay be assigned automatically, for example, a default calendar, a fiscalcalendar, academic calendar or other calendar, or a calendar associatedwith a similar cell, related storage policy or other logicallyassociated entity. One example of a graphical user interface forentering calendar customization information is depicted in FIG. 4. Asshown, a calendar name or ID, such as ABC, may be entered in box 405,which may correspond to information or an identifier stored in table 300in column 325. A beginning month may be selected, box 410, such asApril, which may correspond to the first month column 335 in table 300.The beginning month can be, for example, January as in a Gregoriancalendar, or other month, such as April for a fiscal calendar, Septemberfor an academic calendar, or other month, etc. A user may select thiscalendar to use as a default calendar for all storage operations, box415. If box 415 is selected, the non-standard calendar may be used forall storage operations. The starting year for the non-standard calendarmay be selected in box 420, which is the beginning year in thenon-standard calendar and which may correspond to the first year 325 intable 300. The start date for the calendar may be selected in box(es)425, such as Apr. 16, 2006. The start date may correspond to a firstdate 340 in table 300. The number of years defined in box 430 mayindicate the duration of the calendar, and may correspond to a number ofyears 330 in table 300.

Months in the non-standard calendar may be defined by a user in thescreen shown in FIG. 5. As shown, a table 500 of months in a year may bedefined in which the number of days 510 for each month 505 and the startdate for the month 515 are customized. The number of days 510 may bespecified which will also set the subsequent month's start date. Forexample, as shown, the ABC calendar includes twelve months, each ofwhich has a different number of days. As shown, it may be convenient toprovide months with days corresponding to a number of weeks, such as 21,28, 35, etc. Alternatively, any random number of days may be assigned toa month. The first day in the year is Apr. 16, 2006, and the calendarmodule, month module, day module, offset module, or other module, may beused to automatically calculate a month's starting date 515 based on apredefined number of days in a month 510 and the month 505, or tocalculate a number of days in a month 510 based on a specified month'sstarting date 515.

Turning now to FIG. 6, which depicts a flow diagram for a method forperforming a storage operation, calendar customization preferences maybe received, step 550. The calendar customization preferences may bereceived as described herein. For example, a user may input preferencesfor month start dates, number of days in a month, number of months in ayear, beginning month of a year, or other non-standard calendarpreference. The non-standard calendar preferences may be associated witha storage policy, step 555. The non-standard calendar may be associatedwith a storage policy by, for example, storing an indicator, link,pointer or other reference that indicates an association of the storagepolicy and non-standard calendar in a database, table or index. One suchtable for storing an association between a storage policy andnon-standard calendar may be the table depicted in FIG. 3, in which anon-standard calendar has an associated storage policy 365.

As described herein, a storage policy may include information orpreferences for performing a storage operation. A storage manager mayconsult a storage policy and its associated non-standard calendar toinitiate a storage operation, step 560. For example, a storage policymay indicate that a client should retain a copy of data for six months.The non-standard calendar associated with the storage policy willautomatically calculate or otherwise determine the term for the sixmonth period to perform the storage operation for this storage policy.For example, if a non-standard calendar is created in which a month has28 days, a copy of data retained for six months is actually retained forsix 28 day periods, and not six standard calendar months. In anotherexample, if a non-standard calendar is created in which a calendar yearbegins April 16.sup.th, and a storage operation is to be performed onthe third day of each calendar year, the storage operation will beinitiated on April 19.sup.th. The storage manager, calendar module orother system component may automatically calculate the appropriate timefor the storage operation to initiate based on the storage policy andthe non-standard calendar, and initiate the storage operation,accordingly.

Referring to FIG. 7, a non-standard calendar can also be created, asdescribed herein, and set to be associated with one or more storagepolicies, step 590, by storage data indicating the association of thecalendar and storage policy in a database, index or table. For example,as shown in FIG. 3, a specified calendar, e.g. in column 320 may beassociated with a storage policy in column 365. A storage policy may beassociated with each of a plurality of cells, step 595, for example, bystoring information indicating the association of the storage policy andthe cell in a database, table or index. For example, a cell that isassociated with an application, group of users, geographical location,or other group, may be associated with a storage policy. The cell may beassociated with the storage policy by storing an indication of therelationship between the cell and storage policy in a database, table orindex.

With the storage policy, non-standard calendar and cell information, astorage manager may initiate a storage operation according to thestorage policy and calendar, step 600. In general, to initiate or directa storage operation, a storage manager consults its index or database toobtain storage policy information, which may include associations with astorage operation cell and a non-standard calendar. Thus, the storagemanager, jobs agent, management agent or other component may schedulestorage operations based on the storage policy, cell information,non-standard calendar, or other storage preferences. One example of suchoperation may be that a storage policy dictates that a storageoperation, such as selective deletion, selective copy of electronicdata, a backup or other transfer of electronic data may be performed

Selective deletion of electronic data may be performed by establishing aselection criterion that may be a property or characteristic of a dataitem that is used to select the data item for deletion, or other storageoperations. The same selection criteria may be used to selectively copydata, e.g., selecting data based on the selection criteria to be copied.The selection criteria may be based on time, such as the time the dataitem was stored, cycle, such as a number of cycles occurred or storageoperations performed since the data was stored, application type, datatype, user that generated the data, or other selection criteria. Aselection criteria that relates to time can be used together with anon-standard calendar. For example, a time based selection criteria maybe that a data item is to be deleted (in a selective deletion operation)or copied (in a selective copy operation) if it is more than three yearsold. A non-standard calendar may set forth that a year is twelve 28-daymonths. In that scenario, a three-year old data item is actually lessthan three standard years old. However, a storage manager or othersystem component can automatically count a time-based selection criteriaaccording to an associated non-standard calendar to correctly determinethe relevant time period.

A selection criteria may also be used in extended retention operations.For example, a criterion may be specified relating to a retentionpreference and/or aging preference, such as a time period to retain adata item before aging the data off by either deleting the data orcreating a copy for long term storage. The retention preference may bespecified that a particular data item, or a class of data items, such asa particular data type, application type, client, user generating thedata, or other class, may be retained for three years. The retentionpreference may be associated with a non-standard calendar so that astorage manager or other system component may determine the time periodthat a retention preference of three years corresponds to in thenon-standard calendar.

One way to associate a non-standard calendar and a particular storageoperation is by input by a user or administrator. Referring to FIG. 8,which depicts a graphical user interface, properties or preferences toperforming a storage operation may be named as specified in box 625. Thestorage operation may then be associated with a calendar, such as astandard or non-standard calendar (e.g., as shown the ABC calendardefined in FIGS. 3-5, or other calendar) by selecting box 630. Theassociation of the storage operation 625 and calendar 630 causes alloperations relating to the storage operation to be performed based onthe selected calendar 630. Other information about the storageoperation, such as a default destination, e.g., a library, media agent,drive pool and scratch pool may be set in box 635.

Details relating to the storage operation may be entered in thegraphical user interfaces depicted in FIGS. 9 and 10. In screen 650 and700, a time zone 655 may be selected for the storage operation. Apattern for scheduling a storage operation may be set in areas 660 asonce, daily, weekly, monthly, yearly, or other time interval.Alternatively, a schedule pattern shown in FIG. 9 may be set as acertain number of months in box 665, on a particular day of a month inbox 670, and the calendar the schedule is based on, may be selected asstandard or non-standard (e.g. as shown, the ABC calendar defined inFIGS. 3-5, or other calendar) in box 675. The scheduling pattern shownin FIG. 10 also includes a box for a specific data to perform a storageoperation, or a day of a week of a certain month in box 667, using acalendar (standard or non-standard) specified in box 675. Otherscheduling patterns that may be entered include for example, a day of aweek, hour of a day, or other time.

The schedule pattern may be automatically determined according to anassociated non-standard calendar. For example, as shown in FIG. 9, astorage operation scheduled to occur monthly (660) on day 28 of a month(665, 670), using the ABC calendar (675) which is defined in referenceto FIGS. 3-5, may be initiated on a start date May 14, 2006 (690) whichcorresponds to the 28.sup.th day of the first month of the ABC calendar,which begins on Apr. 16, 2006. In another example, as shown in FIG. 10,a storage operation set to be initiated on a first Monday of March (667)in the ABC calendar (675) which is defined in reference to FIGS. 3-5,the first Monday of March may be automatically calculated to be Mar. 19,2007 (690) since the ABC calendar begins Apr. 16, 2006.

A time of day for performing the storage operation may be entered in box680, 685. In general, the time of day for performing the storageoperation may take into consideration scheduling of system resources forperforming storage operations. A time window may also be set in box 695which may set forth an end time for the defined storage operation. Forexample, as shown, a storage operation definition may be set through aparticular date, number of cycles, other end point, or it may be openended. In the event that the storage operation definition is defined tonever end (695), the storage manager, calendar module, or other systemcomponent may automatically predict an extended term for a non-standardcalendar associated with the storage operation definition which mayoverride a defined term, such as that a calendar is defined for twoyears.

Referring to FIG. 11, which depicts a flow diagram for performing astorage operation, a storage operation request may be received, step720. In general, a storage manager may receive a request to perform astorage operation from a user or administrator, or in accordance with astorage operation initiator automatically issued according to a storagepolicy or other system instruction. The storage manager may identify thedata relevant to the storage operation request, step 725. The storageoperation request may include information about the data relevant to thestorage operation request or alternatively, the storage manager mayobtain the data information by consulting a database or index. The datarelevant to the storage operation request may also be identifiedaccording to a selection criteria, which may be included in a storageoperation request, a storage policy, user inputted, or otherwiseprovided. The selection criteria may relate to data. For example, theselection criteria may be data type, application type, cell group, orbased on a user, organization, geographic location, client, or othercriteria. A storage manager, media agent or other component may consulta database, table or index to identify data satisfying the selectioncriteria. Alternatively, a media agent, or other component, may readdata headers to identify data, or other method to identify data based ona selection criteria.

When the data item has been identified, a storage manager may consult adatabase or index to determine whether a non-standard calendar isassociated with the data item, step 730. For example, the storagemanager may consult a table such as the table shown in FIG. 3.Alternatively, information relating to a non-standard calendar may beincluded in a storage operation request. In the event that nonon-standard calendar is associated with a data item, the storageoperation may be scheduled and performed using a standard calendar, step735. In some cases, a non-standard calendar may be associated with adata item, however the term or duration of the non-standard calendar hasended. When the non-standard calendar is not longer valid, an alert maybe sent to a system administrator which notifies the administrator ofthe non-standard calendar problem, and the storage manager may performthe storage operation according to a standard calendar. Alternatively, astorage manager, calendar module or other system component may attemptto predict a further term for the expired non-standard calendar byapplying some or all preferences in an expired non-standard calendar toa time period following the term of the expired non-standard calendar.

If a non-standard calendar is associated with the identified data item,a non-standard calendar customization module may provide thenon-standard calendar to a storage manager, and the storage manager, orother component may determine a time to perform a storage operationbased on the non-standard calendar, step 740. For example, if a storagepolicy sets forth that a storage operation is to occur at a frequency ofonce per month at the beginning of a month and a non-standard calendardictates that a month begins on the 5.sup.th of the month and the firstmonth is February, the storage manager or other component determinesthat the first storage operation according to the storage policy shouldoccur on the 5.sup.th of February, then the 5.sup.th of March, then the5.sup.th of April, and so on. On these determined times, the storagemanager may initiate the storage operation to be performed by systemcomponents, step 745.

FIG. 12 depicts a graphical user interface which may be used toassociate a non-standard calendar with a storage policy, selective copyoperation or an extended retention operation. As shown, screen 750includes a box for a copy name, 755, which may be used to name a copy.Details relating to the storage operation may be entered in area 760relating to, for example, using a primary copy or other copy forperforming a storage operation, a number of streams to use in thestorage operation, enabling inline copying, automatic copying, setting atime to create an auxiliary copy, such as deferring a time, selecting acalendar, such as a standard calendar or non-standard calendar, or otherstorage operation detail. In addition, destination details may also beentered in area 770 relating to library, media agent, drive pool orscratch pool to use in a storage operation.

Further details relating to a storage operation may also be enteredrelating to a selective copy operation as shown in FIG. 13. FIG. 13depicts a graphical user interface 790 for setting storage operationdetails for a selective copy operation. As shown, backups in a selectivecopy operation may be manually selected, or according to a frequency795, which may be weekly, daily, monthly, or other time period. Thefrequency 795 for performing the selective copy operation may also beset using a non-standard calendar. Thus, for a defined non-standardcalendar in which a month has 28 days, a selective copy operation set tobe performed monthly will be initiated every 28 days according to thenon-standard calendar and not according to a month in a standardcalendar. The frequency 795 can be further specified to occur on aparticular day, 800. The selective copy operation details may alsoinclude the data copy to be used, e.g., a first full backup, last fullbackup or other copy, 805. In addition, the selective copy operation maybe linked to an auxiliary copy operation, 810, to streamline one or morecopy operations.

Details relating to an extended retention operation may be entered in agraphical user interface, such as the screen 825 shown in FIG. 14. Asshown data may be aged by selecting box 830. Alternatively, data may bemanaged using magnetic data. Rules may be set forth for aging data bysetting aging rules, such as infinite, or according to a time period orcycles 835. Extended rules may be set up for extended retention in area840, such as time periods to keep selected copies, or setting a flexibletime period for initiating a retention operation. In general, based onthe rules entered in screen 825, a storage manager may direct a mediaagent to identify data satisfying a selection criteria, such as a typeof copy, data type, or other criteria. Identified data satisfying theselection criteria may be retained according to the rule.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described herein. Software and other modulesmay reside on servers, workstations, personal computers, computerizedtablets, PDAs, and other devices suitable for the purposes describedherein. Software and other modules may be accessible via local memory,via a network, via a browser or other application in an ASP context, orvia other means suitable for the purposes described herein. Datastructures described herein may comprise computer files, variables,programming arrays, programming structures, or any electronicinformation storage schemes or methods, or any combinations thereof,suitable for the purposes described herein. User interface elementsdescribed herein may comprise elements from graphical user interfaces,command line interfaces, and other interfaces suitable for the purposesdescribed herein. Screenshots presented and described herein can bedisplayed differently as known in the art to input, access, change,manipulate, modify, alter, and work with information.

While the invention has been described and illustrated in connectionwith preferred embodiments, many variations and modifications as will beevident to those skilled in this art may be made without departing fromthe spirit and scope of the invention, and the invention is thus not tobe limited to the precise details of methodology or construction setforth above as such variations and modification are intended to beincluded within the scope of the invention.

1. A method for performing a storage operation, the method comprising:storing a plurality of calendars, the calendars comprising at least aGregorian calendar and a non-Gregorian calendar; receiving a firststorage policy, the first storage policy defining one or more storageoperations to perform on one or more data items, the first storagepolicy associated with the Gregorian calendar; performing with one ormore computer processors the storage operations associated with firststorage policy by using the Gregorian calendar; receiving a secondstorage policy, the second storage policy defining one or more storageoperations to perform on one or more data items, the second storagepolicy associated with the non-Gregorian calendar; and performing withone or more computer processors the storage operations associated withthe second storage policy by using the non-Gregorian calendar.
 2. Themethod of claim 1 further comprising transmitting an alert when astorage operation time comprises a time after a first term of thenon-Gregorian calendar expires.
 3. The method of claim 1 furthercomprising predicting a second term of the non-Gregorian calendar,wherein a first term and a second term of the non-Gregorian calendarinclude at least one common time flexible preference.
 4. The method ofclaim 1 wherein the one or more storage operations associated withnon-Gregorian calendar of the second storage policy, comprises aselective copy operation.
 5. The method of claim 1 wherein the one ormore storage operations associated with the non-Gregorian calendar ofthe second storage policy comprises a retention operation.
 6. The methodof claim 1 wherein the non-Gregorian calendar is defined by a user.
 7. Amethod for scheduling a storage operation, the method comprising:associating in a storage system a first storage policy with a standardcalendar, the first storage policy comprising a first frequency forperforming one or more storage operations; associating in the storagesystem a second storage policy with a non-standard calendar, the secondstorage policy comprising a second frequency for performing one or morestorage operations; determining with one or more computer processorswhen to perform the first frequency of the storage operations associatedwith the first storage policy based on the standard calendar; anddetermining with one or more computer processors when to perform thesecond frequency of the storage operations associated with the secondstorage policy based on the non-standard calendar.
 8. The method ofclaim 7 further comprising transmitting an alert when a storageoperation time comprises a time after a first term of the non-standardcalendar expires.
 9. The method of claim 7 further comprising predictinga second term of the non-standard calendar, wherein a first term and asecond term of the non-standard calendar include at least one commontime flexible preference.
 10. The method of claim 7 wherein the one ormore storage operations associated with the non-standard calendar of thesecond storage policy, comprises a selective copy operation.
 11. Themethod of claim 7 wherein the one or more storage operations associatedwith the non-standard calendar of the second storage policy comprises aretention operation.
 12. The method of claim 7 wherein the non-standardcalendar is defined by a user.
 13. The method of claim 7 wherein thesecond frequency associated with the non-standard calendar is convertedinto a third frequency associated with the standard calendar.
 14. Astorage management system for scheduling a storage operation, thestorage management system comprising: a storage device configured tostore a plurality of data items and a plurality of calendars, theplurality of calendars comprising at least a standard calendar and anon-standard calendar; a first storage policy configured to define oneor more storage operations to perform on one or more data items, thefirst storage policy associated with the standard calendar; a secondstorage policy configured to define one or more storage operations toperform on one or more data items, the second storage policy associatedwith the non-standard calendar; and a storage manager configured todetermine with one or more computer processors a first time to performthe at least one storage operation according to the first storagepolicy, the first time relating to the standard calendar and wherein thestorage manager is further configured to determine a second time toperform the least one storage operation according to the second storagepolicy, the second time relating to the non-standard calendar.
 15. Thestorage management system of claim 14 wherein the storage manager isconfigured to transmit an alert when a storage operation time comprisesa time after a first term of the non-standard calendar expires.
 16. Thestorage management system of claim 14 wherein a first term and a secondterm of the non-standard calendar include at least one common timeflexible preference.
 17. The storage management system of claim 14wherein the one or more storage operations associated with non-standardcalendar of the second storage policy, comprises a selective copyoperation.
 18. The storage management system of claim 14 wherein the oneor more storage operations associated with the non-standard calendar ofthe second storage policy comprises a retention operation.
 19. Thestorage management system of claim 14 wherein the non-standard calendaris defined by a user.
 20. The storage management system of claim 14wherein the second time associated with the non-standard calendar isconverted into a third time associated with the standard calendar.